Usage Note 34467: "Unable to log in" or "Unable to deploy platform services" when attempting to log into SAS® Information Map Studio
 |  |  |  |  |
If the run-time value of your Java system property user.name includes an ampersand (&), or if the path for the output log file contains an &, you will be unable to log into SAS Information Map Studio. The message that you see depends on which version of SAS Information Map Studio that you are running.
Version 4.2 or later
If you are running version 4.2 or later, then you see the following error message:
Error trying to deploy platform services. com.sas.services.deployment.ServiceDeploymentException: A SAS foundation service failed to deploy. Caused by: [com.sas.services.ServiceException: Unable to obtain service from factory class com.sas.services.logging.LoggingServiceFactory.] Caused by: [java.lang.IllegalArgumentException: Unable to parse XML document. The entity name must immediately follow the '&' in the entity reference.] Unable to parse XML document. The entity name must immediately follow the '&' in the entity reference.
Version 3.1
If you are running version 3.1, then you see the following error message:
Unable to log in.
Probable cause is an invalid user ID/password.
Please verify that they are correct.
com.sas.services.discovery.ServiceNotAvailableException: Service not available.
Requested service template was ServiceTemplate {
ServiceTypes {
1. interface com.sas.services.user.UserServiceInterface
2. interface com.sas.entities.EntityKeyInterface
3. interface com.sas.services.RemoteServiceInterface
4. interface java.rmi.Remote
5. interface com.sas.services.mgmt.ServiceNotificationBroadcasterInterface
}
Resolving this issue
Checking the user.name
If you see one of these messages, you can determine if the user.name is the cause by submitting the following code in a SAS session. This code returns a list of your current Java system properties:
proc javainfo all;
run;
|
Here is some sample output. Note that the user.name value is sasuser&. This user name would cause the error message to appear. To resolve this issue, log into your computer with a user name that does not include an ampersand.
java.version = 1.4.2_09
java.vm.version = 1.4.2_09-b05
java.home = C:\PROGRA~1\SAS\SHARED~1\JRE\1499C1~1.2_0
java.class.path = C:\Program Files\SAS\SAS 9.1\core\sasmisc\sas.launcher.jar
java.ext.dirs = C:\PROGRA~1\SAS\SHARED~1\JRE\1499C1~1.2_0\lib\ext
java.security.policy = C:\Program Files\SAS\SAS 9.1\core\sasmisc\sas.policy
javaplugin.version = <no value>
sas.jre = private
PFS_TEMPLATE = C:\Program Files\SAS\SAS 9.1\core\sasmisc\qrpfstpt.xml
java.vendor = Sun Microsystems Inc.
java.vendor.url = http://java.sun.com/
java.vm.specification.version = 1.0
java.vm.specification.vendor = Sun Microsystems Inc.
java.vm.specification.name = Java Virtual Machine Specification
java.vm.vendor = Sun Microsystems Inc.
java.vm.name = Java HotSpot(TM) Client VM
java.specification.version = 1.4
java.specification.vendor = Sun Microsystems Inc.
java.specification.name = Java Platform API Specification
java.class.version = 48.0
os.name = Windows XP
os.arch = x86
os.version = 5.1
file.separator = \
path.separator = ;
line.separator =
user.name = sasuser&
user.home = C:\Documents and Settings\sasuser&
user.dir = C:\Documents and Settings\sasuser&
NOTE: PROCEDURE JAVAINFO used (Total process time):
real time 0.01 seconds
cpu time 0.00 secondsChecking the %USERPROFILE%
The path of the output log file is determined, in part, by the %USERPROFILE% environment variable. To determine the value of that variable, submit echo %userprofile% on a command line. If the returned path includes an &, then you will experience this problem. As a workaround, you can change the value of the environment variable so that it does not include a path with an &, or you can turn on diagnostics for SAS Information Map Studio, and manually modify the output log file path each time that you launch SAS Information Map Studio, as explained next.
In the SAS Information Map Studio installation directory, open the mapstudio.ini file in a plain text editor. Modify the last line in the file to be as follows:
MainClass=com.sas.apps.mapStudio.MapStudio -loggingSetupDialog
|
Start up SAS Information Map Studio. A Diagnostic Settings dialog box appears. In the Log file box, either enter a path that does not include an & or clear the box. This value is not saved. You must edit the path each time that you launch the application.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Information Map Studio | Microsoft® Windows® for x64 | 3.1 | 4.31_M2 | 9.1 TS1M3 SP4 | 9.3 TS1M2 |
| Microsoft Windows 2000 Advanced Server | 3.1 | 9.1 TS1M3 SP4 | ||||
| Microsoft Windows 2000 Datacenter Server | 3.1 | 9.1 TS1M3 SP4 | ||||
| Microsoft Windows 2000 Server | 3.1 | 9.1 TS1M3 SP4 | ||||
| Microsoft Windows 2000 Professional | 3.1 | 9.1 TS1M3 SP4 | ||||
| Microsoft Windows NT Workstation | 3.1 | 9.1 TS1M3 SP4 | ||||
| Microsoft Windows Server 2003 Datacenter Edition | 3.1 | 4.31_M2 | 9.1 TS1M3 SP4 | 9.3 TS1M2 | ||
| Microsoft Windows Server 2003 Enterprise Edition | 3.1 | 4.31_M2 | 9.1 TS1M3 SP4 | 9.3 TS1M2 | ||
| Microsoft Windows Server 2003 Standard Edition | 3.1 | 4.31_M2 | 9.1 TS1M3 SP4 | 9.3 TS1M2 | ||
| Microsoft Windows XP Professional | 3.1 | 4.31_M2 | 9.1 TS1M3 SP4 | 9.3 TS1M2 | ||